Apparatus and method to identify the source of an interrupt

ABSTRACT

An apparatus and method for processing non-maskable interrupt source information. For example, one embodiment of a processor comprises: a plurality of cores comprising execution circuitry to execute instructions and process data; local interrupt circuitry comprising a plurality of registers to store interrupt-related data including non-maskable interrupt (NMI) data related to a first NMI; and non-maskable interrupt (NMI) processing mode selection circuitry, responsive to a request, to select between at least two NMI processing modes to process the first NMI including: a first NMI processing mode in which the plurality of registers are to store first data related to a first NMI, wherein no NMI source information related to a source of the NMI is included in the first data, and a second NMI processing mode in which the plurality of registers are to store both the first data related to the first NMI and second data comprising NMI source information indicating the NMI source.

BACKGROUND Field of the Invention

The embodiments of the invention relate generally to the field of computer processors. More particularly, the embodiments relate to an apparatus and method to identify the source of an interrupt including a non-maskable interrupt.

Description of the Related Art

Non-Maskable Interrupts (NMIs) are used to communicate critical events that require an Operating System to take action immediately. There are several reasons why an NMI could be signaled. Since the nature of interrupt delivery has no source that generated the NMI, its required to call all the potential handlers, consuming time and working against the timely handling of NMIs. Some examples of NMI include, but are not limited to the following:

-   -   Panic button in some enterprise servers.     -   Performance monitoring to collect precise events for sampling.     -   Watchdog timers to detect deadlocks in the kernel.     -   Software inter-processor interrupts (IPIs) for taking critical         action (e.g., coordinating for a critical system shutdown).

BRIEF DESCRIPTION OF THE DRAWINGS

A better understanding of the present invention can be obtained from the following detailed description in conjunction with the following drawings, in which:

FIGS. 1A and 1B are block diagrams illustrating a generic vector friendly instruction format and instruction templates thereof according to embodiments of the invention;

FIGS. 2A-C are block diagrams illustrating an exemplary VEX instruction format according to embodiments of the invention;

FIG. 3 is a block diagram of a register architecture according to one embodiment of the invention; and

FIG. 4A is a block diagram illustrating both an exemplary in-order fetch, decode, retire pipeline and an exemplary register renaming, out-of-order issue/execution pipeline according to embodiments of the invention;

FIG. 4B is a block diagram illustrating both an exemplary embodiment of an in-order fetch, decode, retire core and an exemplary register renaming, out-of-order issue/execution architecture core to be included in a processor according to embodiments of the invention;

FIG. 5A is a block diagram of a single processor core, along with its connection to an on-die interconnect network;

FIG. 5B illustrates an expanded view of part of the processor core in FIG. 5A according to embodiments of the invention;

FIG. 6 is a block diagram of a single core processor and a multicore processor with integrated memory controller and graphics according to embodiments of the invention;

FIG. 7 illustrates a block diagram of a system in accordance with one embodiment of the present invention;

FIG. 8 illustrates a block diagram of a second system in accordance with an embodiment of the present invention;

FIG. 9 illustrates a block diagram of a third system in accordance with an embodiment of the present invention;

FIG. 10 illustrates a block diagram of a system on a chip (SoC) in accordance with an embodiment of the present invention;

FIG. 11 illustrates a block diagram contrasting the use of a software instruction converter to convert binary instructions in a source instruction set to binary instructions in a target instruction set according to embodiments of the invention;

FIG. 12 illustrates one embodiment of an interrupt management arrangement comprising local APICs and system-level APICs;

FIG. 13 illustrates various components of one embodiment of a local APIC;

FIG. 14 illustrates a control register to store an indication of an NMI processing mode;

FIG. 15 illustrates one embodiment of a local vector table in a local APIC;

FIG. 16 illustrates one embodiment of an interrupt command register (ICR);

FIG. 17 illustrates one embodiment of a interrupt remapping table entry;

FIG. 18 illustrates one embodiment of a posted interrupt descriptor; and

FIG. 19 illustrates a method in accordance with one embodiment of the invention.

DETAILED DESCRIPTION

In the following description, for the purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of the embodiments of the invention described below. It will be apparent, however, to one skilled in the art that the embodiments of the invention may be practiced without some of these specific details. In other instances, well-known structures and devices are shown in block diagram form to avoid obscuring the underlying principles of the embodiments of the invention.

Exemplary Processor Architectures, Instruction Formats, and Data Types

An instruction set includes one or more instruction formats. A given instruction format defines various fields (number of bits, location of bits) to specify, among other things, the operation to be performed (opcode) and the operand(s) on which that operation is to be performed. Some instruction formats are further broken down though the definition of instruction templates (or subformats). For example, the instruction templates of a given instruction format may be defined to have different subsets of the instruction format's fields (the included fields are typically in the same order, but at least some have different bit positions because there are less fields included) and/or defined to have a given field interpreted differently. Thus, each instruction of an ISA is expressed using a given instruction format (and, if defined, in a given one of the instruction templates of that instruction format) and includes fields for specifying the operation and the operands. For example, an exemplary ADD instruction has a specific opcode and an instruction format that includes an opcode field to specify that opcode and operand fields to select operands (source1/destination and source2); and an occurrence of this ADD instruction in an instruction stream will have specific contents in the operand fields that select specific operands.

Embodiments of the instruction(s) described herein may be embodied in different formats. Additionally, exemplary systems, architectures, and pipelines are detailed below. Embodiments of the instruction(s) may be executed on such systems, architectures, and pipelines, but are not limited to those detailed.

Generic Vector Friendly Instruction Format

A vector friendly instruction format is an instruction format that is suited for vector instructions (e.g., there are certain fields specific to vector operations). While embodiments are described in which both vector and scalar operations are supported through the vector friendly instruction format, alternative embodiments use only vector operations the vector friendly instruction format.

FIGS. 1A-1B are block diagrams illustrating a generic vector friendly instruction format and instruction templates thereof according to embodiments of the invention. FIG. 1A is a block diagram illustrating a generic vector friendly instruction format and class A instruction templates thereof according to embodiments of the invention; while FIG. 1B is a block diagram illustrating the generic vector friendly instruction format and class B instruction templates thereof according to embodiments of the invention. Specifically, a generic vector friendly instruction format 100 for which are defined class A and class B instruction templates, both of which include no memory access 105 instruction templates and memory access 120 instruction templates. The term generic in the context of the vector friendly instruction format refers to the instruction format not being tied to any specific instruction set.

While embodiments of the invention will be described in which the vector friendly instruction format supports the following: a 64 byte vector operand length (or size) with 32 bit (4 byte) or 64 bit (8 byte) data element widths (or sizes) (and thus, a 64 byte vector consists of either 16 doubleword-size elements or alternatively, 8 quadword-size elements); a 64 byte vector operand length (or size) with 16 bit (2 byte) or 8 bit (1 byte) data element widths (or sizes); a 32 byte vector operand length (or size) with 32 bit (4 byte), 64 bit (8 byte), 16 bit (2 byte), or 8 bit (1 byte) data element widths (or sizes); and a 16 byte vector operand length (or size) with 32 bit (4 byte), 64 bit (8 byte), 16 bit (2 byte), or 8 bit (1 byte) data element widths (or sizes); alternative embodiments may support more, less and/or different vector operand sizes (e.g., 256 byte vector operands) with more, less, or different data element widths (e.g., 128 bit (16 byte) data element widths).

The class A instruction templates in FIG. 1A include: 1) within the no memory access 105 instruction templates there is shown a no memory access, full round control type operation 110 instruction template and a no memory access, data transform type operation 115 instruction template; and 2) within the memory access 120 instruction templates there is shown a memory access, temporal 125 instruction template and a memory access, non-temporal 130 instruction template. The class B instruction templates in FIG. 1B include: 1) within the no memory access 105 instruction templates there is shown a no memory access, write mask control, partial round control type operation 112 instruction template and a no memory access, write mask control, vsize type operation 117 instruction template; and 2) within the memory access 120 instruction templates there is shown a memory access, write mask control 127 instruction template.

The generic vector friendly instruction format 100 includes the following fields listed below in the order illustrated in FIGS. 1A-1B.

Format field 140—a specific value (an instruction format identifier value) in this field uniquely identifies the vector friendly instruction format, and thus occurrences of instructions in the vector friendly instruction format in instruction streams. As such, this field is optional in the sense that it is not needed for an instruction set that has only the generic vector friendly instruction format.

Base operation field 142—its content distinguishes different base operations.

Register index field 144—its content, directly or through address generation, specifies the locations of the source and destination operands, be they in registers or in memory. These include a sufficient number of bits to select N registers from a P×Q (e.g. 32×512, 16×128, 32×1024, 64×1024) register file. While in one embodiment N may be up to three sources and one destination register, alternative embodiments may support more or less sources and destination registers (e.g., may support up to two sources where one of these sources also acts as the destination, may support up to three sources where one of these sources also acts as the destination, may support up to two sources and one destination).

Modifier field 146—its content distinguishes occurrences of instructions in the generic vector instruction format that specify memory access from those that do not; that is, between no memory access 105 instruction templates and memory access 120 instruction templates. Memory access operations read and/or write to the memory hierarchy (in some cases specifying the source and/or destination addresses using values in registers), while non-memory access operations do not (e.g., the source and destinations are registers). While in one embodiment this field also selects between three different ways to perform memory address calculations, alternative embodiments may support more, less, or different ways to perform memory address calculations. Augmentation operation field 150—its content distinguishes which one of a variety of different operations to be performed in addition to the base operation. This field is context specific. In one embodiment of the invention, this field is divided into a class field 168, an alpha field 152, and a beta field 154. The augmentation operation field 150 allows common groups of operations to be performed in a single instruction rather than 2, 3, or 4 instructions.

Scale field 160—its content allows for the scaling of the index field's content for memory address generation (e.g., for address generation that uses 2^(scale)*index+base).

Displacement Field 162A—its content is used as part of memory address generation (e.g., for address generation that uses 2^(scale)*index+base+displacement).

Displacement Factor Field 162B (note that the juxtaposition of displacement field 162A directly over displacement factor field 162B indicates one or the other is used)—its content is used as part of address generation; it specifies a displacement factor that is to be scaled by the size of a memory access (N)—where N is the number of bytes in the memory access (e.g., for address generation that uses 2^(scale)*index+base+scaled displacement). Redundant low-order bits are ignored and hence, the displacement factor field's content is multiplied by the memory operands total size (N) in order to generate the final displacement to be used in calculating an effective address. The value of N is determined by the processor hardware at runtime based on the full opcode field 174 (described later herein) and the data manipulation field 154C. The displacement field 162A and the displacement factor field 162B are optional in the sense that they are not used for the no memory access 105 instruction templates and/or different embodiments may implement only one or none of the two.

Data element width field 164—its content distinguishes which one of a number of data element widths is to be used (in some embodiments for all instructions; in other embodiments for only some of the instructions). This field is optional in the sense that it is not needed if only one data element width is supported and/or data element widths are supported using some aspect of the opcodes.

Write mask field 170—its content controls, on a per data element position basis, whether that data element position in the destination vector operand reflects the result of the base operation and augmentation operation. Class A instruction templates support merging-writemasking, while class B instruction templates support both merging- and zeroing-writemasking. When merging, vector masks allow any set of elements in the destination to be protected from updates during the execution of any operation (specified by the base operation and the augmentation operation); in other one embodiment, preserving the old value of each element of the destination where the corresponding mask bit has a 0. In contrast, when zeroing vector masks allow any set of elements in the destination to be zeroed during the execution of any operation (specified by the base operation and the augmentation operation); in one embodiment, an element of the destination is set to 0 when the corresponding mask bit has a 0 value. A subset of this functionality is the ability to control the vector length of the operation being performed (that is, the span of elements being modified, from the first to the last one); however, it is not necessary that the elements that are modified be consecutive. Thus, the write mask field 170 allows for partial vector operations, including loads, stores, arithmetic, logical, etc. While embodiments of the invention are described in which the write mask field's 170 content selects one of a number of write mask registers that contains the write mask to be used (and thus the write mask field's 170 content indirectly identifies that masking to be performed), alternative embodiments instead or additional allow the mask write field's 170 content to directly specify the masking to be performed.

Immediate field 172—its content allows for the specification of an immediate. This field is optional in the sense that is it not present in an implementation of the generic vector friendly format that does not support immediate and it is not present in instructions that do not use an immediate.

Class field 168—its content distinguishes between different classes of instructions. With reference to FIGS. 1A-B, the contents of this field select between class A and class B instructions. In FIGS. 1A-B, rounded corner squares are used to indicate a specific value is present in a field (e.g., class A 168A and class B 168B for the class field 168 respectively in FIGS. 1A-B).

Instruction Templates of Class A

In the case of the non-memory access 105 instruction templates of class A, the alpha field 152 is interpreted as an RS field 152A, whose content distinguishes which one of the different augmentation operation types are to be performed (e.g., round 152A.1 and data transform 152A.2 are respectively specified for the no memory access, round type operation 110 and the no memory access, data transform type operation 115 instruction templates), while the beta field 154 distinguishes which of the operations of the specified type is to be performed. In the no memory access 105 instruction templates, the scale field 160, the displacement field 162A, and the displacement scale filed 162B are not present.

No-Memory Access Instruction Templates—Full Round Control Type Operation

In the no memory access full round control type operation 110 instruction template, the beta field 154 is interpreted as a round control field 154A, whose content(s) provide static rounding. While in the described embodiments of the invention the round control field 154A includes a suppress all floating point exceptions (SAE) field 156 and a round operation control field 158, alternative embodiments may support may encode both these concepts into the same field or only have one or the other of these concepts/fields (e.g., may have only the round operation control field 158).

SAE field 156—its content distinguishes whether or not to disable the exception event reporting; when the SAE field's 156 content indicates suppression is enabled, a given instruction does not report any kind of floating-point exception flag and does not raise any floating point exception handler.

Round operation control field 158—its content distinguishes which one of a group of rounding operations to perform (e.g., Round-up, Round-down, Round-towards-zero and Round-to-nearest). Thus, the round operation control field 158 allows for the changing of the rounding mode on a per instruction basis. In one embodiment of the invention where a processor includes a control register for specifying rounding modes, the round operation control field's 150 content overrides that register value.

No Memory Access Instruction Templates—Data Transform Type Operation

In the no memory access data transform type operation 115 instruction template, the beta field 154 is interpreted as a data transform field 1546, whose content distinguishes which one of a number of data transforms is to be performed (e.g., no data transform, swizzle, broadcast).

In the case of a memory access 120 instruction template of class A, the alpha field 152 is interpreted as an eviction hint field 1526, whose content distinguishes which one of the eviction hints is to be used (in FIG. 1A, temporal 1526.1 and non-temporal 1526.2 are respectively specified for the memory access, temporal 125 instruction template and the memory access, non-temporal 130 instruction template), while the beta field 154 is interpreted as a data manipulation field 154C, whose content distinguishes which one of a number of data manipulation operations (also known as primitives) is to be performed (e.g., no manipulation; broadcast; up conversion of a source; and down conversion of a destination). The memory access 120 instruction templates include the scale field 160, and optionally the displacement field 162A or the displacement scale field 1626.

Vector memory instructions perform vector loads from and vector stores to memory, with conversion support. As with regular vector instructions, vector memory instructions transfer data from/to memory in a data element-wise fashion, with the elements that are actually transferred is dictated by the contents of the vector mask that is selected as the write mask.

Memory Access Instruction Templates—Temporal

Temporal data is data likely to be reused soon enough to benefit from caching. This is, however, a hint, and different processors may implement it in different ways, including ignoring the hint entirely.

Memory Access Instruction Templates—Non-Temporal

Non-temporal data is data unlikely to be reused soon enough to benefit from caching in the 1st-level cache and should be given priority for eviction. This is, however, a hint, and different processors may implement it in different ways, including ignoring the hint entirely.

Instruction Templates of Class B

In the case of the instruction templates of class B, the alpha field 152 is interpreted as a write mask control (Z) field 152C, whose content distinguishes whether the write masking controlled by the write mask field 170 should be a merging or a zeroing.

In the case of the non-memory access 105 instruction templates of class B, part of the beta field 154 is interpreted as an RL field 157A, whose content distinguishes which one of the different augmentation operation types are to be performed (e.g., round 157A.1 and vector length (VSIZE) 157A.2 are respectively specified for the no memory access, write mask control, partial round control type operation 112 instruction template and the no memory access, write mask control, VSIZE type operation 117 instruction template), while the rest of the beta field 154 distinguishes which of the operations of the specified type is to be performed. In the no memory access 105 instruction templates, the scale field 160, the displacement field 162A, and the displacement scale filed 162B are not present.

In the no memory access, write mask control, partial round control type operation 110 instruction template, the rest of the beta field 154 is interpreted as a round operation field 159A and exception event reporting is disabled (a given instruction does not report any kind of floating-point exception flag and does not raise any floating point exception handler).

Round operation control field 159A—just as round operation control field 158, its content distinguishes which one of a group of rounding operations to perform (e.g., Round-up, Round-down, Round-towards-zero and Round-to-nearest). Thus, the round operation control field 159A allows for the changing of the rounding mode on a per instruction basis. In one embodiment of the invention where a processor includes a control register for specifying rounding modes, the round operation control field's 150 content overrides that register value.

In the no memory access, write mask control, VSIZE type operation 117 instruction template, the rest of the beta field 154 is interpreted as a vector length field 159B, whose content distinguishes which one of a number of data vector lengths is to be performed on (e.g., 128, 256, or 512 byte).

In the case of a memory access 120 instruction template of class B, part of the beta field 154 is interpreted as a broadcast field 157B, whose content distinguishes whether or not the broadcast type data manipulation operation is to be performed, while the rest of the beta field 154 is interpreted the vector length field 159B. The memory access 120 instruction templates include the scale field 160, and optionally the displacement field 162A or the displacement scale field 162B.

With regard to the generic vector friendly instruction format 100, a full opcode field 174 is shown including the format field 140, the base operation field 142, and the data element width field 164. While one embodiment is shown where the full opcode field 174 includes all of these fields, the full opcode field 174 includes less than all of these fields in embodiments that do not support all of them. The full opcode field 174 provides the operation code (opcode).

The augmentation operation field 150, the data element width field 164, and the write mask field 170 allow these features to be specified on a per instruction basis in the generic vector friendly instruction format.

The combination of write mask field and data element width field create typed instructions in that they allow the mask to be applied based on different data element widths.

The various instruction templates found within class A and class B are beneficial in different situations. In some embodiments of the invention, different processors or different cores within a processor may support only class A, only class B, or both classes. For instance, a high performance general purpose out-of-order core intended for general-purpose computing may support only class B, a core intended primarily for graphics and/or scientific (throughput) computing may support only class A, and a core intended for both may support both (of course, a core that has some mix of templates and instructions from both classes but not all templates and instructions from both classes is within the purview of the invention). Also, a single processor may include multiple cores, all of which support the same class or in which different cores support different class. For instance, in a processor with separate graphics and general purpose cores, one of the graphics cores intended primarily for graphics and/or scientific computing may support only class A, while one or more of the general purpose cores may be high performance general purpose cores with out of order execution and register renaming intended for general-purpose computing that support only class B. Another processor that does not have a separate graphics core, may include one more general purpose in-order or out-of-order cores that support both class A and class B. Of course, features from one class may also be implement in the other class in different embodiments of the invention. Programs written in a high level language would be put (e.g., just in time compiled or statically compiled) into an variety of different executable forms, including: 1) a form having only instructions of the class(es) supported by the target processor for execution; or 2) a form having alternative routines written using different combinations of the instructions of all classes and having control flow code that selects the routines to execute based on the instructions supported by the processor which is currently executing the code.

VEX Instruction Format

VEX encoding allows instructions to have more than two operands, and allows SIMD vector registers to be longer than 28 bits. The use of a VEX prefix provides for three-operand (or more) syntax. For example, previous two-operand instructions performed operations such as A=A+B, which overwrites a source operand. The use of a VEX prefix enables operands to perform nondestructive operations such as A=B+C.

FIG. 2A illustrates an exemplary AVX instruction format including a VEX prefix 202, real opcode field 230, Mod R/M byte 240, SIB byte 250, displacement field 262, and IMM8 272. FIG. 2B illustrates which fields from FIG. 2A make up a full opcode field 274 and a base operation field 241. FIG. 2C illustrates which fields from FIG. 2A make up a register index field 244.

VEX Prefix (Bytes 0-2) 202 is encoded in a three-byte form. The first byte is the Format Field 290 (VEX Byte 0, bits [7:0]), which contains an explicit C4 byte value (the unique value used for distinguishing the C4 instruction format). The second-third bytes (VEX Bytes 1-2) include a number of bit fields providing specific capability. Specifically, REX field 205 (VEX Byte 1, bits [7-5]) consists of a VEX.R bit field (VEX Byte 1, bit [7]-R), VEX.X bit field (VEX byte 1, bit [6]-X), and VEX.B bit field (VEX byte 1, bit[5]-B). Other fields of the instructions encode the lower three bits of the register indexes as is known in the art (rrr, xxx, and bbb), so that Rrrr, Xxxx, and Bbbb may be formed by adding VEX.R, VEX.X, and VEX.B. Opcode map field 215 (VEX byte 1, bits [4:0]-mmmmm) includes content to encode an implied leading opcode byte. W Field 264 (VEX byte 2, bit [7]-W)—is represented by the notation VEX.W, and provides different functions depending on the instruction. The role of VEX.vvvv 220 (VEX Byte 2, bits [6:3]-vvvv) may include the following: 1) VEX.vvvv encodes the first source register operand, specified in inverted (1 s complement) form and is valid for instructions with 2 or more source operands; 2) VEX.vvvv encodes the destination register operand, specified in 1 s complement form for certain vector shifts; or 3) VEX.vvvv does not encode any operand, the field is reserved and should contain 1111b. If VEX.L 268 Size field (VEX byte 2, bit [2]-L)=0, it indicates 28 bit vector; if VEX.L=1, it indicates 256 bit vector. Prefix encoding field 225 (VEX byte 2, bits [1:0]-pp) provides additional bits for the base operation field 241.

Real Opcode Field 230 (Byte 3) is also known as the opcode byte. Part of the opcode is specified in this field.

MOD R/M Field 240 (Byte 4) includes MOD field 242 (bits [7-6]), Reg field 244 (bits [5-3]), and R/M field 246 (bits [2-0]). The role of Reg field 244 may include the following: encoding either the destination register operand or a source register operand (the rrr of Rrrr), or be treated as an opcode extension and not used to encode any instruction operand. The role of R/M field 246 may include the following: encoding the instruction operand that references a memory address, or encoding either the destination register operand or a source register operand.

Scale, Index, Base (SIB)—The content of Scale field 250 (Byte 5) includes SS252 (bits [7-6]), which is used for memory address generation. The contents of SIB.xxx 254 (bits [5-3]) and SIB.bbb 256 (bits [2-0]) have been previously referred to with regard to the register indexes Xxxx and Bbbb.

The Displacement Field 262 and the immediate field (IMM8) 272 contain data.

Exemplary Register Architecture

FIG. 3 is a block diagram of a register architecture 300 according to one embodiment of the invention. In the embodiment illustrated, there are 32 vector registers 310 that are 512 bits wide; these registers are referenced as zmm0 through zmm31. The lower order 256 bits of the lower 6 zmm registers are overlaid on registers ymm0-15. The lower order 128 bits of the lower 6 zmm registers (the lower order 128 bits of the ymm registers) are overlaid on registers xmm0-15.

General-purpose registers 325—in the embodiment illustrated, there are sixteen 64-bit general-purpose registers that are used along with the existing x86 addressing modes to address memory operands. These registers are referenced by the names RAX, RBX, RCX, RDX, RBP, RSI, RDI, RSP, and R8 through R15.

Scalar floating point stack register file (x87 stack) 345, on which is aliased the MMX packed integer flat register file 350—in the embodiment illustrated, the x87 stack is an eight-element stack used to perform scalar floating-point operations on 32/64/80-bit floating point data using the x87 instruction set extension; while the MMX registers are used to perform operations on 64-bit packed integer data, as well as to hold operands for some operations performed between the MMX and XMM registers.

Alternative embodiments of the invention may use wider or narrower registers. Additionally, alternative embodiments of the invention may use more, less, or different register files and registers.

Exemplary Core Architectures, Processors, and Computer Architectures

Processor cores may be implemented in different ways, for different purposes, and in different processors. For instance, implementations of such cores may include: 1) a general purpose in-order core intended for general-purpose computing; 2) a high performance general purpose out-of-order core intended for general-purpose computing; 3) a special purpose core intended primarily for graphics and/or scientific (throughput) computing. Implementations of different processors may include: 1) a CPU including one or more general purpose in-order cores intended for general-purpose computing and/or one or more general purpose out-of-order cores intended for general-purpose computing; and 2) a coprocessor including one or more special purpose cores intended primarily for graphics and/or scientific (throughput). Such different processors lead to different computer system architectures, which may include: 1) the coprocessor on a separate chip from the CPU; 2) the coprocessor on a separate die in the same package as a CPU; 3) the coprocessor on the same die as a CPU (in which case, such a coprocessor is sometimes referred to as special purpose logic, such as integrated graphics and/or scientific (throughput) logic, or as special purpose cores); and 4) a system on a chip that may include on the same die the described CPU (sometimes referred to as the application core(s) or application processor(s)), the above described coprocessor, and additional functionality. Exemplary core architectures are described next, followed by descriptions of exemplary processors and computer architectures. Detailed herein are circuits (units) that comprise exemplary cores, processors, etc.

Exemplary Core Architectures

FIG. 4A is a block diagram illustrating both an exemplary in-order pipeline and an exemplary register renaming, out-of-order issue/execution pipeline according to embodiments of the invention. FIG. 4B is a block diagram illustrating both an exemplary embodiment of an in-order architecture core and an exemplary register renaming, out-of-order issue/execution architecture core to be included in a processor according to embodiments of the invention. The solid lined boxes in FIGS. 4A-B illustrate the in-order pipeline and in-order core, while the optional addition of the dashed lined boxes illustrates the register renaming, out-of-order issue/execution pipeline and core. Given that the in-order aspect is a subset of the out-of-order aspect, the out-of-order aspect will be described.

In FIG. 4A, a processor pipeline 400 includes a fetch stage 402, a length decode stage 404, a decode stage 406, an allocation stage 408, a renaming stage 410, a scheduling (also known as a dispatch or issue) stage 412, a register read/memory read stage 414, an execute stage 416, a write back/memory write stage 418, an exception handling stage 422, and a commit stage 424.

FIG. 4B shows processor core 490 including a front end unit 430 coupled to an execution engine unit 450, and both are coupled to a memory unit 470. The core 490 may be a reduced instruction set computing (RISC) core, a complex instruction set computing (CISC) core, a very long instruction word (VLIW) core, or a hybrid or alternative core type. As yet another option, the core 490 may be a special-purpose core, such as, for example, a network or communication core, compression engine, coprocessor core, general purpose computing graphics processing unit (GPGPU) core, graphics core, or the like.

The front end unit 430 includes a branch prediction unit 432 coupled to an instruction cache unit 434, which is coupled to an instruction translation lookaside buffer (TLB) 436, which is coupled to an instruction fetch unit 438, which is coupled to a decode unit 440. The decode unit 440 (or decoder) may decode instructions, and generate as an output one or more micro-operations, micro-code entry points, microinstructions, other instructions, or other control signals, which are decoded from, or which otherwise reflect, or are derived from, the original instructions. The decode unit 440 may be implemented using various different mechanisms. Examples of suitable mechanisms include, but are not limited to, look-up tables, hardware implementations, programmable logic arrays (PLAs), microcode read only memories (ROMs), etc. In one embodiment, the core 490 includes a microcode ROM or other medium that stores microcode for certain macroinstructions (e.g., in decode unit 440 or otherwise within the front end unit 430). The decode unit 440 is coupled to a rename/allocator unit 452 in the execution engine unit 450.

The execution engine unit 450 includes the rename/allocator unit 452 coupled to a retirement unit 454 and a set of one or more scheduler unit(s) 456. The scheduler unit(s) 456 represents any number of different schedulers, including reservations stations, central instruction window, etc. The scheduler unit(s) 456 is coupled to the physical register file(s) unit(s) 458. Each of the physical register file(s) units 458 represents one or more physical register files, different ones of which store one or more different data types, such as scalar integer, scalar floating point, packed integer, packed floating point, vector integer, vector floating point, status (e.g., an instruction pointer that is the address of the next instruction to be executed), etc. In one embodiment, the physical register file(s) unit 458 comprises a vector registers unit and a scalar registers unit. These register units may provide architectural vector registers, vector mask registers, and general purpose registers. The physical register file(s) unit(s) 458 is overlapped by the retirement unit 454 to illustrate various ways in which register renaming and out-of-order execution may be implemented (e.g., using a reorder buffer(s) and a retirement register file(s); using a future file(s), a history buffer(s), and a retirement register file(s); using a register maps and a pool of registers; etc.). The retirement unit 454 and the physical register file(s) unit(s) 458 are coupled to the execution cluster(s) 460. The execution cluster(s) 460 includes a set of one or more execution units 462 and a set of one or more memory access units 464. The execution units 462 may perform various operations (e.g., shifts, addition, subtraction, multiplication) and on various types of data (e.g., scalar floating point, packed integer, packed floating point, vector integer, vector floating point). While some embodiments may include a number of execution units dedicated to specific functions or sets of functions, other embodiments may include only one execution unit or multiple execution units that all perform all functions. The scheduler unit(s) 456, physical register file(s) unit(s) 458, and execution cluster(s) 460 are shown as being possibly plural because certain embodiments create separate pipelines for certain types of data/operations (e.g., a scalar integer pipeline, a scalar floating point/packed integer/packed floating point/vector integer/vector floating point pipeline, and/or a memory access pipeline that each have their own scheduler unit, physical register file(s) unit, and/or execution cluster—and in the case of a separate memory access pipeline, certain embodiments are implemented in which only the execution cluster of this pipeline has the memory access unit(s) 464). It should also be understood that where separate pipelines are used, one or more of these pipelines may be out-of-order issue/execution and the rest in-order.

The set of memory access units 464 is coupled to the memory unit 470, which includes a data TLB unit 472 coupled to a data cache unit 474 coupled to a level 2 (L2) cache unit 476. In one exemplary embodiment, the memory access units 464 may include a load unit, a store address unit, and a store data unit, each of which is coupled to the data TLB unit 472 in the memory unit 470. The instruction cache unit 434 is further coupled to a level 2 (L2) cache unit 476 in the memory unit 470. The L2 cache unit 476 is coupled to one or more other levels of cache and eventually to a main memory.

By way of example, the exemplary register renaming, out-of-order issue/execution core architecture may implement the pipeline 400 as follows: 1) the instruction fetch 438 performs the fetch and length decoding stages 402 and 404; 2) the decode unit 440 performs the decode stage 406; 3) the rename/allocator unit 452 performs the allocation stage 408 and renaming stage 410; 4) the scheduler unit(s) 456 performs the schedule stage 412; 5) the physical register file(s) unit(s) 458 and the memory unit 470 perform the register read/memory read stage 414; the execution cluster 460 perform the execute stage 416; 6) the memory unit 470 and the physical register file(s) unit(s) 458 perform the write back/memory write stage 418; 7) various units may be involved in the exception handling stage 422; and 8) the retirement unit 454 and the physical register file(s) unit(s) 458 perform the commit stage 424.

The core 490 may support one or more instructions sets (e.g., the x86 instruction set (with some extensions that have been added with newer versions); the MIPS instruction set of MIPS Technologies of Sunnyvale, Calif.; the ARM instruction set (with optional additional extensions such as NEON) of ARM Holdings of Sunnyvale, Calif.), including the instruction(s) described herein. In one embodiment, the core 490 includes logic to support a packed data instruction set extension (e.g., AVX1, AVX2), thereby allowing the operations used by many multimedia applications to be performed using packed data.

It should be understood that the core may support multithreading (executing two or more parallel sets of operations or threads), and may do so in a variety of ways including time sliced multithreading, simultaneous multithreading (where a single physical core provides a logical core for each of the threads that physical core is simultaneously multithreading), or a combination thereof (e.g., time sliced fetching and decoding and simultaneous multithreading thereafter such as in the Intel® Hyperthreading technology).

While register renaming is described in the context of out-of-order execution, it should be understood that register renaming may be used in an in-order architecture. While the illustrated embodiment of the processor also includes separate instruction and data cache units 434/474 and a shared L2 cache unit 476, alternative embodiments may have a single internal cache for both instructions and data, such as, for example, a Level 1 (L1) internal cache, or multiple levels of internal cache. In some embodiments, the system may include a combination of an internal cache and an external cache that is external to the core and/or the processor. Alternatively, all of the cache may be external to the core and/or the processor.

Specific Exemplary In-Order Core Architecture

FIGS. 5A-B illustrate a block diagram of a more specific exemplary in-order core architecture, which core would be one of several logic blocks (including other cores of the same type and/or different types) in a chip. The logic blocks communicate through a high-bandwidth interconnect network (e.g., a ring network) with some fixed function logic, memory I/O interfaces, and other necessary I/O logic, depending on the application.

FIG. 5A is a block diagram of a single processor core, along with its connection to the on-die interconnect network 502 and with its local subset of the Level 2 (L2) cache 504, according to embodiments of the invention. In one embodiment, an instruction decoder 500 supports the x86 instruction set with a packed data instruction set extension. An L1 cache 506 allows low-latency accesses to cache memory into the scalar and vector units. While in one embodiment (to simplify the design), a scalar unit 508 and a vector unit 510 use separate register sets (respectively, scalar registers 512 and vector registers 514) and data transferred between them is written to memory and then read back in from a level 1 (L1) cache 506, alternative embodiments of the invention may use a different approach (e.g., use a single register set or include a communication path that allow data to be transferred between the two register files without being written and read back).

The local subset of the L2 cache 504 is part of a global L2 cache that is divided into separate local subsets, one per processor core. Each processor core has a direct access path to its own local subset of the L2 cache 504. Data read by a processor core is stored in its L2 cache subset 504 and can be accessed quickly, in parallel with other processor cores accessing their own local L2 cache subsets. Data written by a processor core is stored in its own L2 cache subset 504 and is flushed from other subsets, if necessary. The ring network ensures coherency for shared data. The ring network is bi-directional to allow agents such as processor cores, L2 caches and other logic blocks to communicate with each other within the chip. Each ring data-path is 1024-bits wide per direction in some embodiments.

FIG. 5B is an expanded view of part of the processor core in FIG. 5A according to embodiments of the invention. FIG. 5B includes an L1 data cache 506A part of the L1 cache 504, as well as more detail regarding the vector unit 510 and the vector registers 514. Specifically, the vector unit 510 is a 6-wide vector processing unit (VPU) (see the 16-wide ALU 528), which executes one or more of integer, single-precision float, and double-precision float instructions. The VPU supports swizzling the register inputs with swizzle unit 520, numeric conversion with numeric convert units 522A-B, and replication with replication unit 524 on the memory input.

Processor with integrated memory controller and graphics

FIG. 6 is a block diagram of a processor 600 that may have more than one core, may have an integrated memory controller, and may have integrated graphics according to embodiments of the invention. The solid lined boxes in FIG. 6 illustrate a processor 600 with a single core 602A, a system agent 610, a set of one or more bus controller units 616, while the optional addition of the dashed lined boxes illustrates an alternative processor 600 with multiple cores 602A-N, a set of one or more integrated memory controller unit(s) 614 in the system agent unit 610, and special purpose logic 608.

Thus, different implementations of the processor 600 may include: 1) a CPU with the special purpose logic 608 being integrated graphics and/or scientific (throughput) logic (which may include one or more cores), and the cores 602A-N being one or more general purpose cores (e.g., general purpose in-order cores, general purpose out-of-order cores, a combination of the two); 2) a coprocessor with the cores 602A-N being a large number of special purpose cores intended primarily for graphics and/or scientific (throughput); and 3) a coprocessor with the cores 602A-N being a large number of general purpose in-order cores. Thus, the processor 600 may be a general-purpose processor, coprocessor or special-purpose processor, such as, for example, a network or communication processor, compression engine, graphics processor, GPGPU (general purpose graphics processing unit), a high-throughput many integrated core (MIC) coprocessor (including 30 or more cores), embedded processor, or the like. The processor may be implemented on one or more chips. The processor 600 may be a part of and/or may be implemented on one or more substrates using any of a number of process technologies, such as, for example, BiCMOS, CMOS, or NMOS.

The memory hierarchy includes one or more levels of cache within the cores 604A-N, a set or one or more shared cache units 606, and external memory (not shown) coupled to the set of integrated memory controller units 614. The set of shared cache units 606 may include one or more mid-level caches, such as level 2 (L2), level 3 (L3), level 4 (L4), or other levels of cache, a last level cache (LLC), and/or combinations thereof. While in one embodiment a ring based interconnect unit 612 interconnects the integrated graphics logic 608, the set of shared cache units 606, and the system agent unit 610/integrated memory controller unit(s) 614, alternative embodiments may use any number of well-known techniques for interconnecting such units. In one embodiment, coherency is maintained between one or more cache units 606 and cores 602-A-N.

In some embodiments, one or more of the cores 602A-N are capable of multi-threading. The system agent 610 includes those components coordinating and operating cores 602A-N. The system agent unit 610 may include for example a power control unit (PCU) and a display unit. The PCU may be or include logic and components needed for regulating the power state of the cores 602A-N and the integrated graphics logic 608. The display unit is for driving one or more externally connected displays.

The cores 602A-N may be homogenous or heterogeneous in terms of architecture instruction set; that is, two or more of the cores 602A-N may be capable of execution the same instruction set, while others may be capable of executing only a subset of that instruction set or a different instruction set.

Exemplary Computer Architectures

FIGS. 7-10 are block diagrams of exemplary computer architectures. Other system designs and configurations known in the arts for laptops, desktops, handheld PCs, personal digital assistants, engineering workstations, servers, network devices, network hubs, switches, embedded processors, digital signal processors (DSPs), graphics devices, video game devices, set-top boxes, micro controllers, cell phones, portable media players, hand held devices, and various other electronic devices, are also suitable. In general, a huge variety of systems or electronic devices capable of incorporating a processor and/or other execution logic as disclosed herein are generally suitable.

Referring now to FIG. 7, shown is a block diagram of a system 700 in accordance with one embodiment of the present invention. The system 700 may include one or more processors 710, 715, which are coupled to a controller hub 720. In one embodiment, the controller hub 720 includes a graphics memory controller hub (GMCH) 790 and an Input/Output Hub (IOH) 750 (which may be on separate chips); the GMCH 790 includes memory and graphics controllers to which are coupled memory 740 and a coprocessor 745; the IOH 750 is couples input/output (I/O) devices 760 to the GMCH 790. Alternatively, one or both of the memory and graphics controllers are integrated within the processor (as described herein), the memory 740 and the coprocessor 745 are coupled directly to the processor 710, and the controller hub 720 in a single chip with the IOH 750.

The optional nature of additional processors 715 is denoted in FIG. 7 with broken lines. Each processor 710, 715 may include one or more of the processing cores described herein and may be some version of the processor 600.

The memory 740 may be, for example, dynamic random access memory (DRAM), phase change memory (PCM), or a combination of the two. For at least one embodiment, the controller hub 720 communicates with the processor(s) 710, 715 via a multi-drop bus, such as a frontside bus (FSB), point-to-point interface, or similar connection 795.

In one embodiment, the coprocessor 745 is a special-purpose processor, such as, for example, a high-throughput MIC processor, a network or communication processor, compression engine, graphics processor, GPGPU, embedded processor, or the like. In one embodiment, controller hub 720 may include an integrated graphics accelerator.

There can be a variety of differences between the physical resources 710, 7155 in terms of a spectrum of metrics of merit including architectural, microarchitectural, thermal, power consumption characteristics, and the like.

In one embodiment, the processor 710 executes instructions that control data processing operations of a general type. Embedded within the instructions may be coprocessor instructions. The processor 710 recognizes these coprocessor instructions as being of a type that should be executed by the attached coprocessor 745. Accordingly, the processor 710 issues these coprocessor instructions (or control signals representing coprocessor instructions) on a coprocessor bus or other interconnect, to coprocessor 745. Coprocessor(s) 745 accept and execute the received coprocessor instructions.

Referring now to FIG. 8, shown is a block diagram of a first more specific exemplary system 800 in accordance with an embodiment of the present invention. As shown in FIG. 8, multiprocessor system 800 is a point-to-point interconnect system, and includes a first processor 870 and a second processor 880 coupled via a point-to-point interconnect 850. Each of processors 870 and 880 may be some version of the processor 600. In one embodiment of the invention, processors 870 and 880 are respectively processors 710 and 715, while coprocessor 838 is coprocessor 745. In another embodiment, processors 870 and 880 are respectively processor 710 coprocessor 745.

Processors 870 and 880 are shown including integrated memory controller (IMC) units 872 and 882, respectively. Processor 870 also includes as part of its bus controller units point-to-point (P-P) interfaces 876 and 878; similarly, second processor 880 includes P-P interfaces 886 and 888. Processors 870, 880 may exchange information via a point-to-point (P-P) interface 850 using P-P interface circuits 878, 888. As shown in FIG. 8, IMCs 872 and 882 couple the processors to respective memories, namely a memory 832 and a memory 834, which may be portions of main memory locally attached to the respective processors.

Processors 870, 880 may each exchange information with a chipset 890 via individual P-P interfaces 852, 854 using point to point interface circuits 876, 894, 886, 898. Chipset 890 may optionally exchange information with the coprocessor 838 via a high-performance interface 892. In one embodiment, the coprocessor 838 is a special-purpose processor, such as, for example, a high-throughput MIC processor, a network or communication processor, compression engine, graphics processor, GPGPU, embedded processor, or the like.

A shared cache (not shown) may be included in either processor or outside of both processors, yet connected with the processors via P-P interconnect, such that either or both processors' local cache information may be stored in the shared cache if a processor is placed into a low power mode.

Chipset 890 may be coupled to a first bus 816 via an interface 896. In one embodiment, first bus 816 may be a Peripheral Component Interconnect (PCI) bus, or a bus such as a PCI Express bus or another I/O interconnect bus, although the scope of the present invention is not so limited.

As shown in FIG. 8, various I/O devices 814 may be coupled to first bus 816, along with a bus bridge 818 which couples first bus 816 to a second bus 820. In one embodiment, one or more additional processor(s) 815, such as coprocessors, high-throughput MIC processors, GPGPU's, accelerators (such as, e.g., graphics accelerators or digital signal processing (DSP) units), field programmable gate arrays, or any other processor, are coupled to first bus 816. In one embodiment, second bus 820 may be a low pin count (LPC) bus. Various devices may be coupled to a second bus 820 including, for example, a keyboard and/or mouse 822, communication devices 827 and a storage unit 828 such as a disk drive or other mass storage device which may include instructions/code and data 830, in one embodiment. Further, an audio I/O 824 may be coupled to the second bus 816. Note that other architectures are possible. For example, instead of the point-to-point architecture of FIG. 8, a system may implement a multi-drop bus or other such architecture.

Referring now to FIG. 9, shown is a block diagram of a second more specific exemplary system 900 in accordance with an embodiment of the present invention. Like elements in FIGS. 8 and 9 bear like reference numerals, and certain aspects of FIG. 8 have been omitted from FIG. 9 in order to avoid obscuring other aspects of FIG. 9.

FIG. 9 illustrates that the processors 870, 880 may include integrated memory and I/O control logic (“CL”) 972 and 982, respectively. Thus, the CL 972, 982 include integrated memory controller units and include I/O control logic. FIG. 9 illustrates that not only are the memories 832, 834 coupled to the CL 872, 882, but also that I/O devices 914 are also coupled to the control logic 872, 882. Legacy I/O devices 915 are coupled to the chipset 890.

Referring now to FIG. 10, shown is a block diagram of a SoC 1000 in accordance with an embodiment of the present invention. Similar elements in FIG. 6 bear like reference numerals. Also, dashed lined boxes are optional features on more advanced SoCs. In FIG. 10, an interconnect unit(s) 1002 is coupled to: an application processor 1010 which includes a set of one or more cores 102A-N, cache units 604A-N, and shared cache unit(s) 606; a system agent unit 610; a bus controller unit(s) 616; an integrated memory controller unit(s) 614; a set or one or more coprocessors 1020 which may include integrated graphics logic, an image processor, an audio processor, and a video processor; an static random access memory (SRAM) unit 1030; a direct memory access (DMA) unit 1032; and a display unit 1040 for coupling to one or more external displays. In one embodiment, the coprocessor(s) 1020 include a special-purpose processor, such as, for example, a network or communication processor, compression engine, GPGPU, a high-throughput MIC processor, embedded processor, or the like.

Embodiments of the mechanisms disclosed herein may be implemented in hardware, software, firmware, or a combination of such implementation approaches. Embodiments of the invention may be implemented as computer programs or program code executing on programmable systems comprising at least one processor, a storage system (including volatile and non-volatile memory and/or storage elements), at least one input device, and at least one output device.

Program code, such as code 830 illustrated in FIG. 8, may be applied to input instructions to perform the functions described herein and generate output information. The output information may be applied to one or more output devices, in known fashion. For purposes of this application, a processing system includes any system that has a processor, such as, for example; a digital signal processor (DSP), a microcontroller, an application specific integrated circuit (ASIC), or a microprocessor.

The program code may be implemented in a high level procedural or object oriented programming language to communicate with a processing system. The program code may also be implemented in assembly or machine language, if desired. In fact, the mechanisms described herein are not limited in scope to any particular programming language. In any case, the language may be a compiled or interpreted language.

One or more aspects of at least one embodiment may be implemented by representative instructions stored on a machine-readable medium which represents various logic within the processor, which when read by a machine causes the machine to fabricate logic to perform the techniques described herein. Such representations, known as “IP cores” may be stored on a tangible, machine readable medium and supplied to various customers or manufacturing facilities to load into the fabrication machines that actually make the logic or processor.

Such machine-readable storage media may include, without limitation, non-transitory, tangible arrangements of articles manufactured or formed by a machine or device, including storage media such as hard disks, any other type of disk including floppy disks, optical disks, compact disk read-only memories (CD-ROMs), compact disk rewritable's (CD-RWs), and magneto-optical disks, semiconductor devices such as read-only memories (ROMs), random access memories (RAMs) such as dynamic random access memories (DRAMs), static random access memories (SRAMs), erasable programmable read-only memories (EPROMs), flash memories, electrically erasable programmable read-only memories (EEPROMs), phase change memory (PCM), magnetic or optical cards, or any other type of media suitable for storing electronic instructions.

Accordingly, embodiments of the invention also include non-transitory, tangible machine-readable media containing instructions or containing design data, such as Hardware Description Language (HDL), which defines structures, circuits, apparatuses, processors and/or system features described herein. Such embodiments may also be referred to as program products.

Emulation (including binary translation, code morphing, etc.)

In some cases, an instruction converter may be used to convert an instruction from a source instruction set to a target instruction set. For example, the instruction converter may translate (e.g., using static binary translation, dynamic binary translation including dynamic compilation), morph, emulate, or otherwise convert an instruction to one or more other instructions to be processed by the core. The instruction converter may be implemented in software, hardware, firmware, or a combination thereof. The instruction converter may be on processor, off processor, or part on and part off processor.

FIG. 11 is a block diagram contrasting the use of a software instruction converter to convert binary instructions in a source instruction set to binary instructions in a target instruction set according to embodiments of the invention. In the illustrated embodiment, the instruction converter is a software instruction converter, although alternatively the instruction converter may be implemented in software, firmware, hardware, or various combinations thereof. FIG. 11 shows a program in a high level language 1102 may be compiled using an first compiler 1104 to generate a first binary code (e.g., x86) 1106 that may be natively executed by a processor with at least one first instruction set core 1116. In some embodiments, the processor with at least one first instruction set core 1116 represents any processor that can perform substantially the same functions as an Intel processor with at least one x86 instruction set core by compatibly executing or otherwise processing (1) a substantial portion of the instruction set of the Intel x86 instruction set core or (2) object code versions of applications or other software targeted to run on an Intel processor with at least one x86 instruction set core, in order to achieve substantially the same result as an Intel processor with at least one x86 instruction set core. The first compiler 1104 represents a compiler that is operable to generate binary code of the first instruction set 1106 (e.g., object code) that can, with or without additional linkage processing, be executed on the processor with at least one first instruction set core 1116. Similarly, FIG. 11 shows the program in the high level language 1102 may be compiled using an alternative instruction set compiler 1108 to generate alternative instruction set binary code 1110 that may be natively executed by a processor without at least one first instruction set core 1114 (e.g., a processor with cores that execute the MIPS instruction set of MIPS Technologies of Sunnyvale, Calif. and/or that execute the ARM instruction set of ARM Holdings of Sunnyvale, Calif.). The instruction converter 1112 is used to convert the first binary code 1106 into code that may be natively executed by the processor without an first instruction set core 1114. This converted code is not likely to be the same as the alternative instruction set binary code 1110 because an instruction converter capable of this is difficult to make; however, the converted code will accomplish the general operation and be made up of instructions from the alternative instruction set. Thus, the instruction converter 1112 represents software, firmware, hardware, or a combination thereof that, through emulation, simulation or any other process, allows a processor or other electronic device that does not have a first instruction set processor or core to execute the first binary code 1106.

Apparatus and Method to Identify the Source of an Interrupt

The embodiments of the invention described below allow the source of an interrupt to be written in a vector field in an interrupt register, even when the delivery mode is a non-maskable interrupt (NMI). On receiving an interrupt, the local interrupt processing circuitry (e.g., the Local APIC) converts this vector field to a bit field encoding an indication of the NMI source.

In one implementation, the operating system (OS) receives the interrupt via an error code and the NMI handler then determines the source of the NMI via the error code. If the interrupt is due to a legacy NMI source that the OS is not able to program, such as the front panel button of the computer system, or an NMI generated from the BIOS via the Advanced Configuration and Power Interface (ACPI), a bit (e.g., bit0) in the vector/error code may be set to indicate a legacy source. In one embodiment, the OS handler calls all legacy sources in sequence to ensure that no interrupts are ignored.

FIG. 12 illustrates an example interrupt delivery architecture in a multi-processor system, configured in accordance with the Advanced Programmable Interrupt Controller (APIC) standard. Each of a plurality of processors and/or cores 1201-1204 include local APIC circuitry 1211-1214, respectively, for transmitting, receiving, and processing interrupt messages. An APIC bus 1220 carries inter-processor interrupts (IPIs) between processors/cores and external interrupts received from other system components via I/O APIC circuitry 1215.

FIG. 13 illustrates additional details of one embodiment of a local APIC 1211. While various specific details are illustrated in FIG. 13, it should be noted that the underlying principles of the invention are not necessarily limited to these specific details. A local vector table (LVT) 1200 includes a set of 32-bit APIC registers, one for each local interrupt to allow software to specify the manner in which the local interrupts are delivered to the corresponding processor cores. One embodiment of the local vector table 1200 includes performance monitoring counters, a timer register, local interrupt registers, thermal sensor interrupt registers and error registers. As discussed below, the LVT 1300 is one of the locations where the NMI source information 1342 may be stored.

Timer circuitry 1205 includes another set of registers including counter registers to implement monitoring/timing associated with the various forms of interrupts. Errors detected during interrupt processing are initially stored in an error status register 1255 and moved to an the local vector table 1200.

The local APIC 1211 queues the fixed interrupts that it accepts in one of two interrupt pending registers: the interrupt request register (IRR) 1222 or in-service register (ISR) 1221. In one embodiment, these are 256-bit read-only registers where each bit represents one of 256 possible vectors. Vectors 0 through 15 are reserved by the APIC. When a local interrupt is sent to the processor/core 1201, acceptance logic 1230 determines whether to accept the interrupt in accordance with an acceptance protocol. If the interrupt is accepted, it is logged into the interrupt request register (IRR) 1222. A prioritizer 1215 transmits the interrupt to the processor core according to the interrupt priority and the the current processor priority stored in the processor priority register (PPR) 1210.

The trigger mode register (TMR) 1223 indicates the trigger mode of the interrupt. Upon acceptance of an interrupt into the IRR 1222, the corresponding TMR bit is cleared for edge-triggered interrupts and set for level triggered interrupts. If a TMR bit is set when a cycle for its corresponding interrupt vector is generated, an EOI message is sent to all I/O APICs. Protocol translation circuitry/logic 1235 couples the local APIC to the system bus and performs translation functions.

In one implementation, the interrupt command register (ICR) 1240 is a 64-bit local APIC register that allows software running on the processor/core 1201 to specify and send inter-processor interrupts (IPIs) to other processors in the system. To send an IPI, the ICR is configured to indicate the type of IPI message to be sent and the destination processor(s)/core(s). All fields of the ICR are read-write by software with the exception of the delivery status field, which is read-only. The act of writing to the low doubleword of the ICR causes the IPI to be sent.

As illustrated in FIG. 13, an operating system (OS) and/or virtual machine monitor VMM 1370 (or other privileged software component) reads and/or writes the various local APIC 1311 registers. In operation, all interrupt destinations provide a vector for normal interrupts which is delivered to the local APIC circuitry 1211 and then to an OS-managed handler 1378. Note that the handlers 1378 component illustrated in FIG. 13 may represent the plurality of different handler types described herein including the NMI handler.

Non-maskable interrupts (NMIs) are delivered via a fixed Vector #2 and the interrupt vector field of the source is not programmed in current implementations. One embodiment of the invention uses this field to specify the interrupt source information. In one particular implementation, the interrupt source information is specified in a mask of 16 bits, where each bit is associated with a specific NMI source. In one implementation, an NMI interface 1380 processes the various new NMI functions described below and updates the local APIC 1311 to identify NMI sources 1390. For example, in FIG. 13, the Interrupt Command Register 1340 and/or local vector table 1300 are updated with NMI source information 1341-1342, respectively. In this implementation, the NMI source information 1341-1342 may be encoded in the interrupt vector field, although the underlying principles of the invention are not necessarily limited to this implementation.

By way of example, and not limitation, bits 8-10 in the Interrupt Command Register (ICR) 1240 indicate the delivery mode for sending IPIs. The Vector field (bits 0-7) is currently ignored for NMIs and system management interrupts (SMIs). In one embodiment of the invention, the NMI interface 1380 writes to this Vector field even when the delivery mode is NMI. On receiving an interrupt, the local APIC 1211 converts this Vector to a bit field such as the 16-bit mask and stores the bit field as the NMI source information 1341-1342 in the ICR 1340, LVT 1300, and/or other local APIC registers.

One embodiment of the processors/cores 1201-1204 support a fast return and event delivery (FRED) implementation which significantly improves performance of the interrupt/exception delivery architecture for modern 64 bit operating systems. In particular, this embodiment replaces delivery through the interrupt descriptor table (IDT), thereby removing the memory accesses and descriptor table loads needed to locate the code, stack segments selectors, and pointers for the event handlers 1378. In addition, deprecation of event/exception delivery for protection rings 1 and 2 reduces latency as the event delivery microcode and/or circuitry does not need to consider these paths. Finally, one embodiment provides separate instructions for returning to the user space and returning to the supervisor space, for an optimal microcode implementation with low latency

In an implementation where FRED is available, the OS 1370 can receive the NMI source 1390 data (e.g., the Vector) via an error code. For other implementations, hardware/microcode stores the NMI source 1390 in a control register such as an MSR (Model Specific Register). This mechanism allows an NMI interface 1380 to obtain the source of the NMI via the error code, and then call the appropriate handler 1378.

The CPUID operation is used to identify whether the processor supports a particular feature. One embodiment of the invention relies on of the reserved fields of CPUID which is not currently allocated. In one particular implementation, CPUID.7.EDX[16]=1 indicates that this processor supports the non-maskable interrupt processing techniques described herein.

In one embodiment, the operating system (OS) 1370 and/or virtual machine monitor (VMM) 1370 (or other privileged software) opts in to NMI source delivery by setting a bit in a control register (CR) 1375. For example, in one implementation, the OS/VMM 1370 generates a request to the processor 1301 to choose NMI source delivery on interrupt notification. FIG. 14 illustrates a embodiment in which a bit 23 1401 is set in register CR4. However, the particular control register and bit is not pertinent to the underlying principles of the invention.

NMI Source Registration

In one embodiment, every potential NMI source 1390 informs the OS/VMM 1370 via NMI interface 1380 which will be called when an NMI is signaled. In one embodiment, this is accomplished via a registration operation directed to the NMI interface 1380 such as:

int register_nmi_handler(type, nmi_handler_fn, private_data);

This function is one example of an interface for callers to register an NMI handler. The “type” variable indicates the type of source that generates the NMI. By way of example, and not limitation, the “type” variable may indicate a local NMI (LOCAL_NMI), an IO NMI (IO_NMI), or a performance NMI (PERF_NMI).

One embodiment of the invention identifies the NMI source 1390 more precisely with a unique NMI source identifier. For example, the following function may be offered by the NMI interface 1380:

int register_nmi_handler(type, int*nmi_source, nmi_handler_fn, private_data);

Here, “*nmi_source” uniquely identifies the NMI source. This identifier may be generated by the interface which programs the NMI source 1390. For instance, when an NMI_IPI is generated, the Interrupt Command Register (ICR) may be used to store the NMI source ID 1341.

Programming NMI Source Identifier

As mentioned, NMI source information may stored/managed in various locations. For example, NMI source information 1341-1342 may be programmed in mask fields within the ICR 1340 and/or the local vector table 1300, respectively. In one embodiment, the value of the vector field encoding the NMI source is 8 bits, which is then translated to a 16-bit bit mask (e.g., in which each bit is associated with a different source). When processing an NMI, the OS/VMM 1370, handlers 1378, and/or NMI interface 1380 can read the bit mask to identify the NMI source.

FIG. 15 illustrates an embodiment of the local vector table 1300 comprising a plurality of 32-bit entries. As indicated in the figure, bits 8:10 indicate the delivery mode, which is coded as “100” for an non-maskable interrupts. As shown, the Vector field bits 0:7, previously ignored for NMIs, are used to store NMI source information 1342A-C for certain entries associated with NMIs. In one embodiment, vector field updater circuitry and/or logic 1542 updates the vector fields with the NMI source information 1342A-C. When an NMI is triggered, an NMI source decoder 1545 reads the NMI source information 1342A-C from the relevant entry in the local vector table 1300 to precisely identify the source of the NMI 1390.

The vector field updater 1542 and NMI source decoder 1545 may be implemented in circuitry, program code, or any combination thereof. For example, in one embodiment, the vector field updater 1542 and NMI source decoder 1545 are implemented by execution circuitry of a processor/core 1201 executing different instruction sequences. In another implementation, the vector field updater 1542 and NMI source decoder 1545 include fixed function circuitry to perform the operations described herein. In one particular implementation, one or both of the vector field updater 1542 and NMI source decoder 1545 are integrated within one or more of the handlers 1378 described herein.

In one embodiment, the vector field may be updated with NMI source information for any of the local vector table entries. The three entries highlighted in FIG. 15 are the CMCI Register (FEED 02F0H) which specifies interrupt delivery when an overflow condition of corrected machine check error count reaches a threshold value occurrs in a machine check bank; and the LINT1 and LINT0 Registers which specifies interrupt delivery when an interrupt is signaled at the LINT1 and LINT0 pins, respectively. Note, however, that the underlying principles of the invention may be implemented with other types of registers and entries.

Specifying NMI Source for Inter Processor Interrupt (IPI)

As mentioned, the interrupt command register (ICR) 1340 is the primary local APIC facility for issuing inter-processor interrupts. One embodiment of the ICR 1340 is a 64-bit local register that allows software executed on the processor/core 1201 to specify and send interrupts to other processors in the system. To send an IPI, the processor sets up the ICR 1340 to indicate the type of IPI message to be sent and the destination processor/core or processors/cores. The act of writing to the low doubleword of the ICR 1340 causes the IPI to be sent.

FIG. 16 illustrates one embodiment of a format used in the ICR 1340 for sending non-maskable inter-processor interrupts (IPIs) to signal other logical processors (identified by destination field 1601) to perform special service functions, such as TLB shootdown operations (e.g., invalidating TLB entries for a specified address or address range). For example, if a logical processor on processor/core 1201 updates virtual-to-physical address mappings for a memory region which is shared by a second logical processor on processor/core 1204, it can send an IPI to processor/core 1204 as a non-maskable interrupt to trigger a TLB shootdown for any mappings corresponding to that memory region.

In the illustrated example, the Vector field of bits 0:7, which are normally ignored for NMIs, is updated with NMI source information 1341. In addition, to identify an NMI, the delivery mode specified in bits 8-10 is set to “100” for an NMI. As described with respect to the LVT 1300, in one embodiment, vector field update circuitry and/or logic 1542 updates the vector fields with the NMI source information 1342A-C. An NMI source decoder 1545 may then read the NMI source information 1342A-C from the ICR 1340 to precisely identify the source of the NMI 1390 (e.g., a processor/core for IPIs).

Specifying NMI Source for External Interrupts via IOMMU

In some implementations, an input-output memory management unit (IOMMU) is used to map regions of system memory to devices other than the processor (e.g., IO devices, graphics processors, DSPs, etc). The IOMMU must also translate interrupts between different domains such as IO domains and processor/core domains. In FIG. 12, for example, the I/O APIC may be a component within an IOMMU for remapping interrupts between domains.

Interrupt-rennapping hardware within the IOMMU includes a memory-resident single-level table, called the Interrupt Remapping Table (IRT). The IRT has a base address and size specified through the Interrupt Remap Table Address Register. Each entry in the table is 128-bits in size and is referred to as Interrupt Remapping Table Entry (IRTE).

FIG. 17 illustrates an IRTE 1701 in accordance with one embodiment of the invention. In particular, the delivery mode is specified by bits 5:7 and is updated to indicate non-maskable interrupt delivery (e.g., using the 3-bit 100 code as previously described). In addition, in one embodiment, bits 16:23 comprising the vector field are updated to indicate non-maskable interrupt source information 1741. When the OS/VMM 1370 is programming entries in the IRTE 1701 it provides the NMI source information 1741 which, in one embodiment, is reserved via the register_nmi_handler( ) function.

As illustrated in FIG. 18, in one implementation, similar updates are made to the Posted Interrupt Descriptors 1801. Typically posted interrupt descriptors are not used for NMI notifications since they are only targets for virtual machines. However, the native OS/VMM 1370 can still use posted internet descriptors 1801 in a manner that they can post process.

In this implementation, the delivery mode is specified in one or more of the reserved fields 1805-1807 of the posted interrupt descriptor format 1801. The NMI source information 1841 may be stored in bits 272:279 as illustrated.

Providing NMI Source on Interrupt Delivery

Regardless of the specified set of registers used, the NMI source information (e.g., 1341) programmed in the vector field is gathered by the local APIC 1311 and delivered using NMI delivery to an OS/VMM handler 1378. In one embodiment, when using Fast Return and Event Delivery (FRED), a 64-bit error code is pushed on the stack, out of which a subset of bits (e.g., 16-bits, 32-bits, etc) are valid. As mentioned, these bits identify which error source signaled the NMI. If bit 0 is set, this indicates one of the legacy sources generated the NMI, and hence the OS/VMM 1370 needs to call all the legacy sources to determine which (if any) generated the interrupt. Otherwise it will be considered a Spurious NMI and the OS/VMM 1370 will take a default action specified by the administrator.

In one embodiment, the delivery is arranged by exposing a specific MSR that the NMI handler 1378 reads to determine the NMI sources 1390 (e.g., via a read MSR (rdmsr( ) instruction). In order to avoid any races which might occur if the bits were set via NMI delivery and the OS/VMM 1370 ensuring it handled the event, one embodiment of the OS/VMM 1370 clears the sources reported by the MSR by writing a 1 to those sources. The interrupt handler 1378 first reads the MSR, and then clears the sources it has taken note of and then writes the same value back. It then proceeds to call the appropriate interrupt handlers. The following code sequence is illustrative of one particular implementation:

nmi_sources=sources=rdmsr(MSR_NMI_SOURCE);

while (sources) {

-   -   val=find_first_bit(sources);     -   call_nmi_callback(val); // Call the appropriate handler     -   sources &=˜(1<<val);

}

// Now clear the MSR so new sources can be processed.

wrmsr(NMI_MSR_SOURCE, nmi_sources);

A method in accordance with one embodiment of the invention is illustrated in FIG. 19. The method may be implemented within the context of the architectures described above, but is not limited to any particular processor or system architecture.

At 1901, an NMI source registers an NMI handler with an OS or VMM indicating NMI source information. As mentioned, in one embodiment, the NMI source information is provided in an error code. At 1902, a non-maskable interrupt (NMI) is received and, at 1903, a control register of the processor receiving the NMI is read to determine whether NMI source delivery is enabled.

If NMI source delivery is not enabled, determined at 1904, then at 1907 data related to the NMI is stored in one or more data fields in local APIC circuitry registers, excluding the NMI source information. At 1908, the NMI is delivered to its destination without NMI source information.

If NMI source delivery is enabled, determined at 1904, then at 1905 data related to the NMI is stored in one or more data fields in local APIC circuitry registers including NMI source information, which is stored in an interrupt vector field of the register(s). At 1906, the NMI is delivered to its destination with the NMI source information.

In the foregoing specification, the embodiments of invention have been described with reference to specific exemplary embodiments thereof. It will, however, be evident that various modifications and changes may be made thereto without departing from the broader spirit and scope of the invention as set forth in the appended claims. The specification and drawings are, accordingly, to be regarded in an illustrative rather than a restrictive sense.

EXAMPLES

The following are example implementations of different embodiments of the invention.

Example 1. A processor comprising: a plurality of cores comprising execution circuitry to execute instructions and process data; local interrupt circuitry comprising a plurality of registers to store interrupt-related data including non-maskable interrupt (NMI) data related to a first NMI; and non-maskable interrupt (NMI) processing mode selection circuitry, responsive to a request, to select between at least two NMI processing modes to process the first NMI including: a first NMI processing mode in which the plurality of registers are to store first data related to a first NMI, wherein no NMI source information related to a source of the NMI is included in the first data, and a second NMI processing mode in which the plurality of registers are to store both the first data related to the first NMI and second data comprising NMI source information indicating the NMI source.

Example 2. The processor of example 1 wherein the first data is to be stored in a first set of fields in the plurality of registers and the second data is to be stored in a second field in at least one of the plurality of registers.

Example 3. The processor of example 2 wherein the second field comprises an interrupt vector field which is not utilized in the first NMI processing mode.

Example 4. The processor of example 3 wherein the interrupt vector field comprises an 8-bit field.

Example 5. The processor of example 3 wherein the first data comprises a delivery mode indication to indicate the first NMI is a non-maskable interrupt.

Example 6. The processor of example 1 wherein the plurality of registers include a local vector table (LVT) and an interrupt command register (ICR).

Example 7. The processor of example 3 wherein the request is generated by an operating system (OS) or virtual machine monitor (VMM), the OS or VMM to receive an error code specifying the NMI source information and to responsively store the second data in the plurality of registers.

Example 8. The processor of example 1 further comprising: an input-output memory management unit (IOMMU) comprising an interrupt remapping table (IRT) to store a portion of the first data when in the first NMI processing mode and to additionally store a portion of the second data when in the second NMI processing mode.

Example 9. A method comprising: executing instructions and processing data on a plurality of cores; storing interrupt-related data including non-maskable interrupt (NMI) data related to a first NMI on local interrupt circuitry comprising a plurality of registers; selecting between at least first and second NMI processing modes to process the first NMI; storing first data in the plurality of registers related to a first NMI when in the first NMI processing mode, wherein no NMI source information related to a source of the NMI is included in the first data; and storing second data in addition to the first data in the plurality of registers related to the first NMI, the second data comprising NMI source information indicating the NMI source.

Example 10. The method of example 9 wherein the first data is to be stored in a first set of fields in the plurality of registers and the second data is to be stored in a second field in at least one of the plurality of registers.

Example 11. The method of example 10 wherein the second field comprises an interrupt vector field which is not utilized in the first NMI processing mode.

Example 12. The method of example 11 wherein the interrupt vector field comprises an 8-bit field.

Example 13. The method of example 11 wherein the first data comprises a delivery mode indication to indicate the first NMI is a non-maskable interrupt.

Example 14. The method of example 9 wherein the plurality of registers include a local vector table (LVT) and an interrupt command register (ICR).

Example 15. The method of example 11 wherein the request is generated by an operating system (OS) or virtual machine monitor (VMM), the OS or VMM to receive an error code specifying the NMI source information and to responsively store the second data in the plurality of registers.

Example 16. The method of example 9 further comprising: storing a portion of the first data in an interrupt remapping table (IRT) of an input-output memory management unit (IOMMU) when in the first NMI processing mode; and additionally storing a portion of the second data in the IRT when in the second NMI processing mode.

Example 17. A machine-readable medium having program code stored thereon which, when executed by a machine, causes the machine to perform the operations of: executing instructions and processing data on a plurality of cores; storing interrupt-related data including non-maskable interrupt (NMI) data related to a first NMI on local interrupt circuitry comprising a plurality of registers; selecting between at least first and second NMI processing modes to process the first NMI; storing first data in the plurality of registers related to a first NMI when in the first NMI processing mode, wherein no NMI source information related to a source of the NMI is included in the first data; and storing second data in addition to the first data in the plurality of registers related to the first NMI, the second data comprising NMI source information indicating the NMI source.

Example 18. The machine-readable medium of claim 17 wherein the first data is to be stored in a first set of fields in the plurality of registers and the second data is to be stored in a second field in at least one of the plurality of registers.

Example 19. The machine-readable medium of example 18 wherein the second field comprises an interrupt vector field which is not utilized in the first NMI processing mode.

Example 20. The machine-readable medium of example 19 wherein the interrupt vector field comprises an 8-bit field.

Example 21. The machine-readable medium of example 19 wherein the first data comprises a delivery mode indication to indicate the first NMI is a non-maskable interrupt.

Example 22. The machine-readable medium of example 17 wherein the plurality of registers include a local vector table (LVT) and an interrupt command register (ICR).

Example 23. The machine-readable medium of claim 19 wherein the request is generated by an operating system (OS) or virtual machine monitor (VMM), the OS or VMM to receive an error code specifying the NMI source information and to responsively store the second data in the plurality of registers.

Example 24. The machine-readable medium of example 17 further comprising: storing a portion of the first data in an interrupt remapping table (IRT) of an input-output memory management unit (IOMMU) when in the first NMI processing mode; and additionally storing a portion of the second data in the IRT when in the second NMI processing mode.

Embodiments of the invention may include various steps, which have been described above. The steps may be embodied in machine-executable instructions which may be used to cause a general-purpose or special-purpose processor to perform the steps. Alternatively, these steps may be performed by specific hardware components that contain hardwired logic for performing the steps, or by any combination of programmed computer components and custom hardware components.

As described herein, instructions may refer to specific configurations of hardware such as application specific integrated circuits (ASICs) configured to perform certain operations or having a predetermined functionality or software instructions stored in memory embodied in a non-transitory computer readable medium. Thus, the techniques shown in the Figures can be implemented using code and data stored and executed on one or more electronic devices (e.g., an end station, a network element, etc.). Such electronic devices store and communicate (internally and/or with other electronic devices over a network) code and data using computer machine-readable media, such as non-transitory computer machine-readable storage media (e.g., magnetic disks; optical disks; random access memory; read only memory; flash memory devices; phase-change memory) and transitory computer machine-readable communication media (e.g., electrical, optical, acoustical or other form of propagated signals—such as carrier waves, infrared signals, digital signals, etc.). In addition, such electronic devices typically include a set of one or more processors coupled to one or more other components, such as one or more storage devices (non-transitory machine-readable storage media), user input/output devices (e.g., a keyboard, a touchscreen, and/or a display), and network connections. The coupling of the set of processors and other components is typically through one or more busses and bridges (also termed as bus controllers). The storage device and signals carrying the network traffic respectively represent one or more machine-readable storage media and machine-readable communication media. Thus, the storage device of a given electronic device typically stores code and/or data for execution on the set of one or more processors of that electronic device. Of course, one or more parts of an embodiment of the invention may be implemented using different combinations of software, firmware, and/or hardware. Throughout this detailed description, for the purposes of explanation, numerous specific details were set forth in order to provide a thorough understanding of the present invention. It will be apparent, however, to one skilled in the art that the invention may be practiced without some of these specific details. In certain instances, well known structures and functions were not described in elaborate detail in order to avoid obscuring the subject matter of the present invention. Accordingly, the scope and spirit of the invention should be judged in terms of the claims which follow. 

What is claimed is:
 1. A processor comprising: a plurality of cores comprising execution circuitry to execute instructions and process data; local interrupt circuitry comprising a plurality of registers to store interrupt-related data including non-maskable interrupt (NMI) data related to a first NMI; and non-maskable interrupt (NMI) processing mode selection circuitry, responsive to a request, to select between at least two NMI processing modes to process the first NMI including: a first NMI processing mode in which the plurality of registers are to store first data related to a first NMI, wherein no NMI source information related to a source of the NMI is included in the first data, and a second NMI processing mode in which the plurality of registers are to store both the first data related to the first NMI and second data comprising NMI source information indicating the NMI source.
 2. The processor of claim 1 wherein the first data is to be stored in a first set of fields in the plurality of registers and the second data is to be stored in a second field in at least one of the plurality of registers.
 3. The processor of claim 2 wherein the second field comprises an interrupt vector field which is not utilized in the first NMI processing mode.
 4. The processor of claim 3 wherein the interrupt vector field comprises an 8-bit field.
 5. The processor of claim 3 wherein the first data comprises a delivery mode indication to indicate the first NMI is a non-maskable interrupt.
 6. The processor of claim 1 wherein the plurality of registers include a local vector table (LVT) and an interrupt command register (ICR).
 7. The processor of claim 3 wherein the request is generated by an operating system (OS) or virtual machine monitor (VMM), the OS or VMM to receive an error code specifying the NMI source information and to responsively store the second data in the plurality of registers.
 8. The processor of claim 1 further comprising: an input-output memory management unit (IOMMU) comprising an interrupt remapping table (IRT) to store a portion of the first data when in the first NMI processing mode and to additionally store a portion of the second data when in the second NMI processing mode.
 9. A method comprising: executing instructions and processing data on a plurality of cores; storing interrupt-related data including non-maskable interrupt (NMI) data related to a first NMI on local interrupt circuitry comprising a plurality of registers; selecting between at least first and second NMI processing modes to process the first NMI; storing first data in the plurality of registers related to a first NMI when in the first NMI processing mode, wherein no NMI source information related to a source of the NMI is included in the first data; and storing second data in addition to the first data in the plurality of registers related to the first NMI, the second data comprising NMI source information indicating the NMI source.
 10. The method of claim 9 wherein the first data is to be stored in a first set of fields in the plurality of registers and the second data is to be stored in a second field in at least one of the plurality of registers.
 11. The method of claim 10 wherein the second field comprises an interrupt vector field which is not utilized in the first NMI processing mode.
 12. The method of claim 11 wherein the interrupt vector field comprises an 8-bit field.
 13. The method of claim 11 wherein the first data comprises a delivery mode indication to indicate the first NMI is a non-maskable interrupt.
 14. The method of claim 9 wherein the plurality of registers include a local vector table (LVT) and an interrupt command register (ICR).
 15. The method of claim 11 wherein the request is generated by an operating system (OS) or virtual machine monitor (VMM), the OS or VMM to receive an error code specifying the NMI source information and to responsively store the second data in the plurality of registers.
 16. The method of claim 9 further comprising: storing a portion of the first data in an interrupt remapping table (IRT) of an input-output memory management unit (IOMMU) when in the first NMI processing mode; and additionally storing a portion of the second data in the IRT when in the second NMI processing mode.
 17. A machine-readable medium having program code stored thereon which, when executed by a machine, causes the machine to perform the operations of: executing instructions and processing data on a plurality of cores; storing interrupt-related data including non-maskable interrupt (NMI) data related to a first NMI on local interrupt circuitry comprising a plurality of registers; selecting between at least first and second NMI processing modes to process the first NMI; storing first data in the plurality of registers related to a first NMI when in the first NMI processing mode, wherein no NMI source information related to a source of the NMI is included in the first data; and storing second data in addition to the first data in the plurality of registers related to the first NMI, the second data comprising NMI source information indicating the NMI source.
 18. The machine-readable medium of claim 17 wherein the first data is to be stored in a first set of fields in the plurality of registers and the second data is to be stored in a second field in at least one of the plurality of registers.
 19. The machine-readable medium of claim 18 wherein the second field comprises an interrupt vector field which is not utilized in the first NMI processing mode.
 20. The machine-readable medium of claim 19 wherein the interrupt vector field comprises an 8-bit field.
 21. The machine-readable medium of claim 19 wherein the first data comprises a delivery mode indication to indicate the first NMI is a non-maskable interrupt.
 22. The machine-readable medium of claim 17 wherein the plurality of registers include a local vector table (LVT) and an interrupt command register (ICR).
 23. The machine-readable medium of claim 19 wherein the request is generated by an operating system (OS) or virtual machine monitor (VMM), the OS or VMM to receive an error code specifying the NMI source information and to responsively store the second data in the plurality of registers.
 24. The machine-readable medium of claim 17 further comprising: storing a portion of the first data in an interrupt remapping table (IRT) of an input-output memory management unit (IOMMU) when in the first NMI processing mode; and additionally storing a portion of the second data in the IRT when in the second NMI processing mode. 